Release Notes
Configuring ActiveMQ
Note: Before any monitoring and remote configuration can be performed, you must first install the Message Queueing Monitoring Agent and create a Monitoring Agent Configuration. First-time users start here
From the ActiveMQ tab, you can manage any number of ActiveMQ brokers.; Each with its own set of properties.
To monitor and control one or more ActiveMQ brokers you must provide some basic connection details.
Configuring the connection
- Add ActiveMQ broker
- Remove ActiveMQ broker
- Enable ActiveMQ broker
- Disable ActiveMQ broker
- Manage Queue thresholds
- Global - Use if not overridden by a specific setting
- Specific - Overrides global configuration on named queue
- Apply exclusion filters
- Authentication
Remember to click on the Save button to persist changes. It may take some time (depending on the user-defined synchronisation interval) for Nodinite to reflect on changes.
Add ActiveMQ broker
Click the Add button to add a new ActiveMQ broker to monitor, repeat as needed.
- Click the Accordion to expand the connection configuration
- Enable ActiveMQ monitoring - When checked this specific ActiveMQ configuration will be monitored
- Configuration name - user-friendly name for this ActiveMQ connection. Also becomes the default Application name for all monitored Resources.
- Description - (optional) user-friendly short description for this configuration.
- Connection String - The connection string used by the Message Queueing Monitoring Agent to connect to the ActiveMQ broker.
Remove ActiveMQ broker
Click the Remove button to remove the configuration for monitoring the ActiveMQ broker with queue Resources to Monitor.
Example of the 'Remove' button to remove ActiveMQ broker configuration from monitoring
Instead of removing an ActiveMQ broker you can simply disable monitoring. This will keep your configuration.
Enable ActiveMQ broker
A disabled Monitoring Configuration is clearly marked with a ban sign. Only disabled brokers can be Enabled.
Disabled ActiveMQ broker has a ban sign to mark the actual broker being disabled
Click the checkbox to re-enable monitoring of ActiveMQ broker related Resources.
ActiveMQ broker Monitoring is enabled when the checkbox is checked
Disable ActiveMQ broker
You can stop monitoring the ActiveMQ broker without removing the configuration by disabling the selected configuration.
An enabled Monitoring Configuration does not have the ban sign. Only enabled ActiveMQ brokers can be Disabled.
Enabled ActiveMQ brokers does not have a ban sign
Un-check the checkbox to disable monitoring of ActiveMQ broker related Resources.
Manage Queue thresholds
Queue settings are either global or overridden with specific settings.
Global Settings
Global settings are used for evaluations of the queues if not specific settings have been set.
- Queue thresholds:
- Number-based evaluation
- Warning Count - 0 means do not evaluate
- Error Count - 0 means do not evaluate
- Time-based evaluation
- Warning Time Span - Timespan format (days.hours:minutes:seconds)
- Error Time Span - Timespan format (days.hours:minutes:seconds)
- Number-based evaluation
- Queue exclusions filter
Number based evaluation
If you select the Fixed option for Count Evaluation Type then monitoring is based on the number of messages in the queue.
0 means do not evaluate
| State | Name | Data Type | Description |
|---|---|---|---|
| Warning Count | integer | The number of messages to go above on the queue to trigger Warning alert | |
| Error Count | integer | The number of messages to go above on the queue to trigger Error alert |
Time-based evaluation
Time-based evaluation is always evaluated. If you do not want to perform evaluation based on time then simply provide long enough thresholds.
Timespan format (days.hours:minutes:seconds)
| State | Name | Data Type | Description |
|---|---|---|---|
| Warning TimeSpan | Timespan 00:05:00 (5 minutes) | The age of first message on the queue to trigger Warning alert | |
| Error TimeSpan | Timespan 01:10:00 (1 hour 10 minutes) | The age of first message on the queue to trigger Error alert |
Queue exclusions filter
Resources can be excluded using a RegEx based filter. You can Add and Remove as many RegEx expressions as you like.
Example #1: Remove all queues that starts with the letter '_'
^[_].*
Example 1: Remove all queues starting with the letter '_'
You can also use the filter to remove everything that do not match your provided RegEx expression, like
^((?!ONLYLIKEMYNAME).)*$
Whenever you apply one or more filters the configuration accordion will reflect this by displaying a filter icon to help you know there is an exclusion filter being used.
Example of filter icon whenever exclusions are configured
We have had many support incidents with reports of missing queues due to this functionality. If you miss out a queue in your Monitor Views then first make sure your filters are not the ones responsible for this. Remember; With great power comes great responsibility
Specific queue settings
You can provide specific thresholds for named queues.
If the actual queue is removed or changes it name, you must reconfigure the specific configuration within Nodinite
From within the Specific queue settings section you can click on the Add button to add a specific configuration.
Next, expand the accordion.
- Queue name - (mandatory) The exact name of the queue to configure
- Description - (optional) user-friendly short description for this configuration.
All other thresholds settings are already documented in the global section.
Specific configurations using Remote Actions are further detailed on the Managing ActiveMQ user guide.
Configure Authentication
- Use Authentication - When checked, this connection is authenticated using the provided credentials.
- User name - The name of the 'User' account with proper access rights
- Password - The password for the user
Next Step
Related
Add or manage a Monitoring Agent Configuration
Install Message Queueing Monitoring Agent